System and method for providing unified communications and collaboration (ucc) connectivity between incompatible systems

ABSTRACT

An improved system and method are disclosed for enabling unified communications and collaboration (UCC) communications between incompatible communication systems. For example, the method may include using a universal UCC (U2C2) gateway in a first system to establish a connection with a server in a second system. The U2C2 gateway mimics a behavior defined for use within the second system when communicating with the server in order to be compatible with the second system. The U2C2 gateway notifies a multipoint control unit (MCU) within the first system of the connection. The MCU manages the UCC session and recognizes the U2C2 gateway as the source and destination for communications corresponding to the connection. The U2C2 gateway normalizes media received from the second system for compatibility with the first system before sending the media to the MCU for the UCC session. The U2C2 gateway also normalizes media received from the MCU for compatibility with the second system before sending the media to the second system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/422,746, filed on Feb. 2, 2017, entitled SYSTEM AND METHOD FOR PROVIDING UNIFIED COMMUNICATIONS AND COLLABORATION (UCC) CONNECTIVITY BETWEEN INCOMPATIBLE SYSTEMS. U.S. patent application Ser. No. 15/422,746 is a continuation of International PCT Application No. PCT/US15/43630, filed on Aug. 4, 2015, entitled SYSTEM AND METHOD FOR PROVIDING UNIFIED COMMUNICATIONS AND COLLABORATION (UCC) CONNECTIVITY BETWEEN INCOMPATIBLE SYSTEMS. International PCT Application No. PCT/US15/43630 claims benefit of and/or priority to U.S. Provisional Application No. 62/033,439, filed on Aug. 5, 2014, entitled SYSTEM AND METHOD FOR PROVIDING UNIFIED COMMUNICATIONS AND COLLABORATION (UCC) CONNECTIVITY BETWEEN INCOMPATIBLE SYSTEMS. Application Ser. No. 15/422,746, PCT/US15/43630 and 62/033,439 are incorporated by reference herein in their entirety.

BACKGROUND

Communications systems often have limitations that affect communications across system boundaries. Accordingly, what is needed are a system and method that addresses such issues.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding, reference is now made to the following description taken in conjunction with the accompanying Drawings in which:

FIG. 1 illustrates one embodiment of an environment with generally incompatible communication systems that may be joined by a universal UCC (U2C2) gateway;

FIG. 2 illustrates a sequence diagram of one embodiment of a process that may be executed to establish a UCC session between the systems of FIG. 1;

FIG. 3 illustrates a sequence diagram of one embodiment of a process that may be executed to transfer media within a UCC session such as that established with respect to FIG. 2;

FIG. 4 illustrates a sequence diagram of another embodiment of a process that may be executed to transfer media within a UCC session such as that established with respect to FIG. 2;

FIG. 5 illustrates a sequence diagram of another embodiment of a process that may be executed to establish a UCC session between the systems of FIG. 1;

FIG. 6 illustrates a flow chart of one embodiment of a process by which a mediator may handle requests within the environment of FIG. 1;

FIG. 7 illustrates a flow chart of one embodiment of a process by which a U2C2 gateway may handle a connection to a third party system within the environment of FIG. 1;

FIG. 8 illustrates a flow chart of one embodiment of a process by which a U2C2 gateway may handle media destined for a third party system within the environment of FIG. 1;

FIG. 9 illustrates a flow chart of one embodiment of a process by which a U2C2 gateway may handle media originating from a third party system within the environment of FIG. 1;

FIG. 10 illustrates another embodiment of an environment with generally incompatible communication systems that may be joined by a U2C2 gateway;

FIG. 11 illustrates a sequence diagram of one embodiment of a process that may be executed to establish a UCC session between the systems of FIG. 10;

FIGS. 12-15 illustrates sequence diagrams of various embodiments of processes that may be executed to transfer media within a UCC session such as that established with respect to FIG. 11;

FIG. 16 illustrates a flow chart of one embodiment of a process by which a U2C2 gateway may handle a connection to a third party system within the environment of FIG. 10;

FIG. 17 illustrates a flow chart of one embodiment of a process by which a U2C2 gateway may handle media originating from a third party system within the environment of FIG. 10;

FIG. 18 illustrates a flow chart of one embodiment of a process by which a U2C2 gateway may handle media destined for a third party system within the environment of FIG. 10;

FIG. 19 illustrates yet another embodiment of an environment with generally incompatible communication systems that may be joined by a U2C2 gateway; and

FIG. 20 illustrates one embodiment of a system that may be used within the environment of FIG. 1.

DETAILED DESCRIPTION

It is understood that the following disclosure provides many different embodiments or examples. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.

Referring to FIG. 1, one embodiment of an environment 100 is illustrated with a communication system 102 and a communication system 104. Each system 102 and 104 provides some level of unified communications and collaboration (UCC) functionality that may include voice, audio, video, instant messaging (IM), presence information, desktop sharing, data sharing, whiteboards, voicemail, e-mail, short message service (SMS) messaging, faxes, and/or other services (all of which may be referred to herein as “media”). It is understood that each system 102 and 104 may provide all of this functionality or may provide only a subset of this functionality.

In the present example, the two systems 102 and 104 provide the UCC functionality using different protocols for communications, which would typically make the two systems 102 and 104 incompatible. In other words, while each system can provide its UCC functionality to users within that system, a user of the system 102 cannot typically communicate with a user of the system 104 as the two systems cannot communicate with one another.

For example, the system 102 may use Amadeo (produced by Damaka, Inc., of Richardson, Tex.) to provide UCC functionality to endpoints 106 and 108. The system 104 may use Lync (produced by Microsoft Corp. of Seattle, Wash.) to provide UCC functionality to endpoints 110 and 112. It is understood that either system 102 and 104 may represent many different systems and Amadeo and Lync are used herein for purposes of example only.

Generally, users of Amadeo and Lync cannot communicate because the systems 102 and 104 are silos and only users within a particular system (and possibly other identical systems if in federated domain relationships) can communicate. For example, Amadeo users can only communicate with other Amadeo users and Lync users can only communicate with other Lync users. Accordingly, users may interact with other users from the same system, but are typically unable to interact with users from the other system or any other system due to the incompatible protocols.

In the present example, the system 104 includes a third party system server/gateway server 114 that may represent one or more servers. For example, the server 114 may represent separate servers that provide UCC functionality to the endpoints 110 and 112, such as a server for audio/video functionality, a server for data functionality, and a server for instant messaging functionality. Alternatively, the server 114 may be a single server that provides multiple components that provide separate channels for the audio/video, data, and instant messaging functionality. In still other embodiments, the server 114 may handle the audio/video, data, and instant messaging functionality in a single channel. In the present embodiment, it does not matter how the server 114 provides the UCC functionality to the endpoints 110 and 112, only that it does so. If the system 104 is a Lync system, the server 114 is a Lync server.

The server 114 also provides a gateway for the system 104 to external networks, such as the system 102. Typically, this enables the system 104 to communicate with other compatible systems and may be used to provide network access (e.g., internet access) to users within the system 104. Depending on the type of system represented by the system 104, the system 104 may be able to form a federated domain relationship with one or more other systems. It is understood that, in some embodiments, the third party system server and the gateway may be on two different servers, although they are combined in the present example.

In the present example, the system 102 includes a multipoint control unit (MCU) 116, a universal UCC (U2C2) gateway 118, and a mediator 120. As will be described below, the U2C2 gateway 118 and the mediator 120 enable the system 102 to communicate with otherwise incompatible systems, such as the system 104, and may not be needed for communications that occur only within the system 102 (e.g., between the endpoints 106 and 108).

The MCU 116 generally operates only within the system 102, although it may include functionality to communicate with other systems in some embodiments. Within the system 102, the MCU 116 is used to provide multipoint UCC functionality to the endpoints 106 and 108. The functionality provided by the U2C2 gateway 118 and the mediator 120 may be used in conjunction with the MCU 116 to extend multipoint UCC conference capabilities to one or more endpoints in other systems, such as the endpoints 110 and 112 in the system 104, and bring those endpoints into a UCC session with one or both of the endpoints 106 and 108.

Generally, an MCU such as the MCU 116 does not initiate communications. More specifically, the MCU 116 will listen for incoming calls, but will not initiate any outgoing messages with endpoints that have not first contacted the MCU. However, in the present example, the MCU 116 has been configured with the mediator 120 to relay messages to endpoints even if those endpoints have not contacted the MCU 116. For example, the mediator 120 may receive an invitation message from the endpoint 106 and relay the message to the endpoint 108. In embodiments where the MCU 116 has not been modified in this manner, the invitation message may be sent to the U2C2 gateway 118 instead of the MCU 116, and the U2C2 gateway 118 would then notify the MCU that there is another connection. In still other embodiments, the mediator 120 may be a separate device from the MCU 116 and the U2C2 gateway 118, and may handle such endpoint messages.

The U2C2 gateway 118 is configured to handle communications between otherwise incompatible networks, such as the system 102 and the system 104. The U2C2 gateway 118 includes a module 122 that enables the U2C2 gateway 118 to communicate with the system 104. More specifically, the module 122 enables the U2C2 gateway 118 to mimic the behavior of the system 104 so that the server 114 believes that the U2C2 gateway 118 is the same type of network as the system 104.

To accomplish this, the module 122 provides the U2C2 gateway 118 with a complete protocol suite for the network type of the system 104. For example, if the server 114 is a Lync server, the module 122 will provide the Lync protocol suite. The protocol suite includes all information needed to communicate with the server 114, including request/response models and security models. In other words, whatever metadata is required by the third party system server 114, the U2C2 gateway 118 will provide through the module 122. Because the U2C2 gateway 118 is presenting itself to the server 114 as the same system type as the server 114, the U2C2 gateway 118 will handle communications in a manner identical to that of the server 114.

The module 122 then translates between the system 104 and the system 102. For example, communications sent from the MCU 116 to the server 114 are received by the U2C2 gateway 118, translated by the U2C2 gateway 118, and sent to the server 114. Similarly, communications sent from the server 114 to the MCU 116 are received by the U2C2 gateway 118, translated by the U2C2 gateway 118, and sent to the server MCU 116.

It is understood that the module 122 may be an integral part of the U2C2 gateway 118, rather than a module. For example, the U2C2 gateway 118 may include the functionality provided by the module 122 rather than obtaining that functionality via the module 122. In the present example, a modular approach is used to simplify the configuration of the U2C2 gateway 118. For example, if the U2C2 gateway 118 is to be configured to communicate with different third party systems, the appropriate module for each system can be loaded into or otherwise provided to the U2C2 gateway 118. Furthermore, changes may be made to a module without affecting the other modules.

Accordingly, rather than requiring an endpoint to dial into the MCU 116 in the conventional passive manner, the U2C2 gateway 118 is able to communicate with other systems and actively pull their endpoints into a UCC session. No changes are required to the third party system or its endpoints. This enables the U2C2 gateway 118 to communicate with any third party system for which it has a module and expands UCC sessions to encompass virtually any type of endpoint.

Referring to FIG. 2, a sequence diagram 200 illustrates one embodiment of a process that may be executed to enable UCC communications between users in the system 102 and users in the system 104. In the present example, the endpoint 106 of the system 102 would like to add the endpoint 110 of the system 104 to a UCC session.

In step 202, the endpoint 106 sends a request to the MCU 116. The request is handled by the mediator 120 (which is part of the MCU 116 in the present embodiment), which identifies that the request is for an endpoint that is not in the system 102 and forwards the request to the U2C2 gateway 118 in step 204. In step 206, the U2C2 gateway 118 establishes a connection with the server 114 using the protocol suite of the server 114.

In step 208, the U2C2 gateway 118 sends a request for services for the endpoint 110 to the server 114 using the protocol suite of the server 114. For example, the request may be for audio, video, and IM services or for any other combination of available UCC services. In step 210, the server 114 establishes a UCC session with the endpoint 110. In step 112, the server 114 responds to the U2C2 gateway 114 with session information and/or media from the endpoint 110. In step 214, the U2C2 gateway 114 notifies the MCU 116 of the new connection.

It is noted that the MCU 116 has no knowledge that the new connection is with an endpoint in another network (e.g., the system 104 instead of the system 102). The MCU 116 treats the new connection just like any other connection from an endpoint within the system 102, and views the U2C2 118 gateway as the source/destination for any media received from that endpoint or sent to that endpoint.

Referring to FIG. 3, a sequence diagram 300 illustrates one embodiment of a process that may be executed to transfer UCC communications between users in the system 102 and users in the system 104. In the present example, the endpoint 110 of the system 104 sends information to the UCC session.

In step 302, the endpoint 110 sends media (e.g., audio, video, and/or chat) to the server 114. In step 304, the server 114 sends the media to the U2C2 gateway 118. As the server 114 is operating using its own protocol suite, there is no need to make any changes to the server 114 in order to enable the server 114 to communicate with the U2C2 gateway 118.

In step 306, the U2C2 gateway 118 normalizes the media received from the server 114. The normalization process converts the media for compatibility with the MCU 116. Without normalization, the MCU 116 would not be able to handle the media from the server 114 due to the differences in protocols. Furthermore, the normalization may be used to convert the media from one codec used by the system 104 to another codec used by the system 102. For example, the U2C2 gateway 118 may have a list of codecs that are used by the MCU 116. If the media received in step 304 is not encoded using one of those codecs, the U2C2 gateway 118 can re-encode the media for the MCU 116 using one of the listed codecs. In step 308, the U2C2 gateway 118 sends the normalized media to the MCU 116.

In step 310, the MCU 116 mixes the media to send to all endpoints in the UCC session that can handle that media type. For example, only endpoints that can handle audio will receive audio content from the MCU 116. In the present example, all endpoints are compatible from a media perspective.

In step 312, the MCU 116 sends the media to the endpoints 106 and 108. In step 314, the MCU 116 sends the media to the U2C2 gateway 118. In step 316, the U2C2 gateway 118 converts the media to be compatible with the server 114, which may include re-encoding as described with respect to step 306. In step 318, the U2C2 gateway 118 sends the converted media to the server 114. In step 320, the server 114 sends the media to the endpoint 112. In the present embodiment, the server 114 does not send the media to the endpoint 110 as the endpoint 110 was the originator of the media, but the server 114 may also send the media to the endpoint 110 in other embodiments.

It is understood that the order of steps 312 and 314 may be reversed in some embodiments. In other embodiments, steps 312 and 314 may occur simultaneously.

Referring to FIG. 4, a sequence diagram 400 illustrates one embodiment of a process that may be executed to transfer UCC communications between users in the system 102 and users in the system 104. In the present example, the endpoint 106 of the system 102 sends information via the UCC session.

In step 402, the endpoint 106 sends media (e.g., audio, video, and/or chat) to the MCU 116. In step 404, the MCU 116 mixes the media to send to all endpoints in the UCC session that can handle that media type. For example, only endpoints that can handle audio will receive audio content from the MCU 116. In the present example, all endpoints are compatible from a media perspective.

In step 406, the MCU 116 sends the media to the endpoint 108. In the present embodiment, the MCU 116 does not send the media to the endpoint 106 as the endpoint 106 was the originator of the media, but the MCU 116 may also send the media to the endpoint 106 in other embodiments.

In step 408, the MCU 116 sends the media to the U2C2 gateway 118. In step 410, the U2C2 gateway 118 converts the media to be compatible with the server 114. In step 412, the U2C2 gateway 118 sends the converted media to the server 116. In step 414, the server 114 sends the media to the endpoints 110 and 112.

It is understood that the order of steps 406 and 408 may be reversed in some embodiments. In other embodiments, steps 406 and 408 may occur simultaneously.

Referring to FIG. 5, a sequence diagram 500 illustrates one embodiment of a process that may be executed to enable UCC communications between users in the system 102 and users in the system 104. In the present example, the endpoint 106 of the system 102 would like to add the endpoint 110 of the system 104 to a UCC session. However, unlike FIG. 2, there is either no mediator 120 or the mediator is part of the U2C2 gateway 118. Accordingly, the endpoint 106 communicates directly with the U2C2 gateway 118.

In step 502, the endpoint 106 sends a request to the U2C2 gateway 118. In step 504, the U2C2 gateway 118 establishes a connection with the server 114 using the protocol suite of the server 114. In step 506, the U2C2 gateway 118 sends a request for services for the endpoint 110 to the server 114 using protocol suite of the server 114. For example, the request may be for audio, video, and IM services or for any other combination of available UCC services.

In step 508, the server 114 establishes a UCC session with the endpoint 110. In step 510, the server 114 responds to the U2C2 gateway 114 with session information and/or media from the endpoint 110. In step 512, the U2C2 gateway 114 notifies the MCU 116 of the new connection.

It is noted that the MCU 116 has no knowledge that the new connection is with an endpoint in another network (e.g., the system 104 instead of the system 102). The MCU 116 treats the new connection just like any other connection from an endpoint within the system 102, and views the U2C2 118 gateway as the source/destination for anything received from that endpoint or sent to that endpoint.

Referring to FIG. 6, a method 600 illustrates one embodiment of a process that may be executed by the mediator 120 of the system 102 of FIG. 1. In step 602, a request is received from an endpoint within the mediator's system, such as the endpoint 106. In step 604, a determination is made as to whether the request is for the addition of an endpoint that is outside of the system 102 or for a connection to the MCU 116 (e.g., asking for the creation of a UCC session or to be added to an existing UCC session). If the request is for the addition of an endpoint, the mediator 120 sends the request to the U2C2 gateway 118 in step 606. If the request is for a connection to the MCU 116, the mediator 120 sends the request to the MCU 116 in step 608.

Referring to FIG. 7, a method 700 illustrates one embodiment of a process that may be executed by the U2C2 gateway 118 of the system 102 of FIG. 1. For purposes of this example, it is understood that the U2C2 gateway 118 includes the appropriate module 122 needed to communicate with the system 104.

In step 702, a request is received from the mediator 120. For example, the request may be sent by the mediator 120 in step 606 of FIG. 6. The request may include information identifying a particular UCC session being handled by the MCU 116. This enables the U2C2 gateway 118 to add the requested connection to the proper UCC session later (in step 708).

In step 704, the U2C2 gateway 118 identifies the third party system (e.g., the system 104) needed for the request. The identification may include obtaining information about the third party system, including the type of system (e.g., the protocol suite used), server/gateway addresses, whether the third party system is in a federated domain relationship with the system 102, and/or similar information needed to establish contact. The identification may include accessing one or more lookup tables, querying a local or remote database, querying the system 104 for information, and/or other taking other steps needed to identify the needed information.

In step 706, the U2C2 gateway 118 establishes a connection to the third party system using the third party system's protocol suite. As previously described, the U2C2 gateway 118 behaves exactly like the third party system from a protocol perspective. In step 708, the U2C2 gateway 118 notifies the MCU 116 that the new connection is to be added to the appropriate UCC session being handled by the MCU 116.

Referring to FIG. 8, a method 800 illustrates one embodiment of a process that may be executed by the U2C2 gateway 118 of the system 102 of FIG. 1. In step 802, media is received from the MCU 116 for a connection being managed by the U2C2 gateway 118 to the third party system 104. In step 804, the U2C2 gateway 118 converts the media for compatibility with the third party system's protocol suite. In step 806, the U2C2 gateway 118 sends the converted media to the third party system 104, which will then distribute the media to the appropriate endpoints.

Referring to FIG. 9, a method 900 illustrates one embodiment of a process that may be executed by the U2C2 gateway 118 of the system 102 of FIG. 1. In step 902, media is received from the third party system 104 for a connection managed by the U2C2 gateway 118. In step 904, the U2C2 gateway 118 converts the media for compatibility with the MCU 116. In step 906, the U2C2 gateway 118 sends the converted media to the MCU 116, which will then mix the media if needed and distribute the media to the appropriate endpoints.

Referring to FIG. 10, one embodiment of an environment 1000 is illustrated with the communication system 102 of FIG. 1 and a communication system 1002. In the present example, unlike the system 104 of FIG. 1, the system 1002 has not exposed any servers/gateways to the U2C2 gateway 118. For example, the system 1002 may be provided by Google Hangouts (as provided by Google Inc., of Mountain View, Calif.) and the U2C2 gateway 118 is unable to communicate directly with servers providing the hangout functionality in the same manner as with the server 114 of FIG. 1.

Accordingly, the U2C2 gateway 118 includes a module 1010. The module 1010 enables the U2C2 gateway 118 to access a login server 1004 that controls access to the third party system's functionality to endpoints such as endpoints 1006 and 1008. Once logged in, the U2C2 gateway 118 is simply an endpoint within the third party system 1002 and is not distinguishable from the endpoints 1006 or 1008 from the perspective of the third party system 1002. The U2C2 gateway 118 can then establish sessions with the endpoints 1006 and 1008, and can include them in UCC sessions via the MCU 116. It is noted that the connections between the U2C2 gateway 118 and the endpoints 1006 and 1008 are not peer to peer connections, but go through the server 1004 that is handling the session in the third party system 1002.

Referring to FIG. 11, a sequence diagram 1100 illustrates one embodiment of a process that may be executed to enable UCC communications between users in the system 102 and users in the system 1002. In the present example, the endpoint 106 of the system 102 would like to add the endpoint 1006 of the system 1002 to a UCC session.

In step 1102, the endpoint 106 sends a request to the MCU 116. The request is handled by the mediator 120 (which is part of the MCU 116 in the present embodiment), which identifies that the request is for an endpoint that is not in the system 102 and forwards the request to the U2C2 gateway 118 in step 1104. In step 1106, the U2C2 gateway 118 logs into the third party system 1002 as an endpoint.

In step 1108, the U2C2 gateway 118 connects to the endpoints 1006 and 1008. This occurs using whatever connection mechanism is provided by the third party system 1002. The U2C2 gateway 118 then notifies the MCU 116 of the new connection. All messages will pass through the U2C2 gateway 118 acting as an endpoint in the system 1002.

Referring to FIGS. 12-14, sequence diagrams 1200, 1300, and 1400, respectively, illustrate embodiments of processes that may be executed to transfer UCC communications between users in the system 102 and users in the system 1002. In the example of FIG. 12, all media originating within the system 1002 is passed back to the server 1004. In the examples of FIGS. 13 and 14, media originating in the system 1002 is not passed back to the server 1004. This may occur, for example, if the server 1004 automatically handles routing of the media back to all participating endpoints within the system 1002, which would cause duplication if the media was also sent back from the U2C2 gateway 118.

Referring specifically to FIG. 12, some of the illustrated steps are similar to those of FIG. 3 and are not described in detail in the present example. In step 1206, the U2C2 gateway 118 takes the media received as an endpoint within the system 1002 and coverts it for the MCU 116. Similarly, in step 1216, the U2C2 gateway 118 coverts the media received from the MCU 116 before sending it to the server 1004 as an endpoint within the system 1002.

Referring specifically to FIG. 13, some of the illustrated steps are similar to those of FIG. 12 and are not described in detail in the present example. However, the server 1004 sends the media to the endpoint 1008 in step 1314 (which can happen at any time after step 1302) without receiving it from the U2C2 gateway 118. The U2C2 gateway 118 has no control over the server 1004 and cannot prevent this, but this makes it undesirable for the U2C2 gateway 118 to send the media to the endpoint 1008 because the endpoint 1008 would receive the media twice.

Accordingly, after receiving the media from the MCU 116 in step 1316, the U2C2 gateway 118 drops the media in step 1318. This means that the endpoint 1008 will only receive a single copy of the media. This may be accomplished, for example, by configuring the U2C2 gateway 118 to filter media received from the MCU 116 by origination tag or another indicator, and to discard any media that originated from the system 1002. By configuring the U2C2 gateway 118 to drop the media, no modification to the MCU 116 or server 1004 is needed.

Referring specifically to FIG. 14, some of the illustrated steps are similar to those of FIG. 13 and are not described in detail in the present example. As in FIG. 13, the server 1004 sends the media to the endpoint 1008 in step 1414 (which can happen at any time after step 1402). The U2C2 gateway 118 has no control over the server 1004 and cannot prevent this, but this makes it undesirable for the U2C2 gateway 118 to send the media to the endpoint 1008. Accordingly, the MCU 116 does not send the media to the U2C2 gateway 118, thereby removing steps 1316 and 1318 of FIG. 13. It is noted that this may require modification of the MCU 116 so that it knows not to return media originating from the U2C2 gateway 118.

Referring to FIG. 15, a sequence diagram 1500 illustrates one embodiment of a process that may be executed to transfer UCC communications between users in the system 102 and users in the system 1002. In the present example, the endpoint 106 of the system 102 sends information via the UCC session. Some of the illustrated steps are similar to those of FIG. 4 and are not described in detail in the present example. It is noted that the issue of FIGS. 13 and 14 is not present in this example as the media is originating from the system 102 and not the system 1002.

In step 1510, the U2C2 gateway 118 takes the media received from the MCU 116 and coverts it for the system 1002. Then, acting as an endpoint within the system 1002, the U2C2 gateway 118 sends the media to the server 1004 in step 1512. The server 1004 then passes the media to the endpoints 1006 and 1008 in step 1514.

Referring to FIG. 16, a method 1600 illustrates one embodiment of a process that may be executed by the U2C2 gateway 118 of the system 102 of FIG. 10. For purposes of this example, it is understood that the U2C2 gateway 118 includes the appropriate module 1002 needed to communicate with the system 1004.

In step 1602, a request is received from the mediator 120. The request may include information identifying a particular UCC session being handled by the MCU 116. This enables the U2C2 gateway 118 to add the requested connection to the proper UCC session later (in step 1608).

In step 1604, the U2C2 gateway 118 identifies the third party system (e.g., the system 1002) needed for the request. The identification may include obtaining information about the third party system, including the server/gateway addresses, login information, and/or similar information needed to establish contact. The identification may include accessing one or more lookup tables, querying a local or remote database, querying the system 1002 for information, and/or other taking other steps needed to identify the needed information.

In step 1606, the U2C2 gateway 118 logs into the third party system 1002 using previously established login credentials (e.g., user name and password). The U2C2 gateway 118 behaves exactly like an endpoint within the third party system 1002. In step 1608, the U2C2 gateway 118 contact the endpoint(s) within the system 1002. In step 1610, the U2C2 gateway 118 notifies the MCU 116 that the new connection is to be added to the appropriate UCC session being handled by the MCU 116.

Referring to FIG. 17, a method 1700 illustrates one embodiment of a process that may be executed by the U2C2 gateway 118 of the system 102 of FIG. 10. In step 1702, media is received from a third party system for a connection managed by the U2C2 gateway 118 (e.g., a third party system within which the U2C2 gateway 118 is present as an endpoint). In step 1704, the U2C2 gateway 118 converts the media for compatibility with the MCU 116. In step 1706, the U2C2 gateway 118 sends the converted media to the MCU 116, which will then mix the media if needed and distribute the media to the appropriate endpoints.

Referring to FIG. 18, a method 1800 illustrates one embodiment of a process that may be executed by the U2C2 gateway 118 of the system 102 of FIG. 10. In step 1802, media is received from the MCU 116 for a connection managed by the U2C2 gateway 118 for the third party system 1002. In step 1804, a determination is made as to the origin of the media. If the media originated from the third party system 1002, the method 1800 moves to step 1806 and discards the media to prevent the media from being duplicated within the system 1002 as described with respect to FIG. 13. If the media originated from the system 102, the method 1800 moves to step 1808.

In step 1808, the U2C2 gateway 118 converts the media for compatibility with the endpoint behavior of the U2C2 gateway 118 within the third party system 1002. In step 1810, the U2C2 gateway 118 sends the converted media to the third party system, which will then distribute the media to the appropriate endpoints.

In embodiments where the U2C2 gateway 118 is not responsible for dropping the media to prevent duplication from occurring, steps 1804 and 1806 may be removed. In such embodiments, either the U2C2 gateway 118 will pass all media through to the system 1002 (as shown in FIG. 12) or the U2C2 gateway 118 will not receive the media from the MCU 116 at all (as shown in FIG. 14).

Referring to FIG. 19, one embodiment of an environment 1900 is illustrated with the communication systems 102 and 104 of FIG. 1 and the communication system 1002 of FIG. 10. Because the U2C2 gateway 118 can connect to many different types of systems and include those systems in a single UCC session, it can pull the endpoints 110, 112, 1006, and 1008 into a single UCC session with each other, as well as with the endpoints 106 and 108.

Furthermore, any system and/or endpoint for which the U2C2 gateway 118 has a module can be included into a UCC session, thereby providing UCC functionality to even non-UCC enabled systems and endpoints. For example, a system 1902 includes a non-UCC enabled gateway 1904 that is coupled to an endpoint 1906. A system 1908 includes a non-UCC enabled endpoint 1910. The U2C2 gateway 118 is able to communicate with the system 1902 via a module 1912 and with the system 1908 via a module 1914. The endpoints 1906 and 1910 can be added to a UCC session with any of the endpoints 106, 108, 110, 112, 1006, 1008, and each other.

For example, the U2C2 gateway 118 can provide as much UCC functionality to an endpoint as can be handled by that endpoint. If the endpoint 110 can handle audio, video, and IM and the endpoint 1910 can only handle IM, then the U2C2 gateway 118 will inform the MCU 116 of those capabilities and the MCU 116 will only mix the media for a particular endpoint based on that endpoint's capabilities. This enables even limited endpoints to participate in a UCC session in whatever way they can and does not require them to have particular capabilities.

For example, an endpoint may use Twitter (provided by Twitter, Inc., of San Francisco, Calif.), Facebook (provided by Facebook, Inc., of Menlo Park, Calif.), Webex (provided by Cisco Systems, Inc., of San Jose, Calif.), Sametime (provided by International Business Machines Corporation (IBM) of Armonk, N.Y.), Facetime (provided by Apple, Inc., of Cupertino, Calif.), and/or any other functionality. An endpoint may have access to Cisco Call Manager (provided by Cisco Systems, Inc., of San Jose, Calif.), a public switched telephone network (PSTN), a session initiation protocol (SIP) gateway, and/or any other network component or network type. The endpoint may be any device that is able to communicate over a network, including such devices as teleconferencing systems provided by Tandberg (provided by Cisco Systems, Inc., of San Jose, Calif.) and Polycom, Inc., of San Jose, Calif. As long as the U2C2 gateway 118 has the access to the modules needed to configure the U2C2 gateway 118 to communicate in the desired manner, an endpoint can have virtually any functionality and be coupled to other endpoints via the U2C2 gateway 118.

Referring to FIG. 20, one embodiment of a system 2000 is illustrated. The system 2000 is one possible example of a device such as an MCU, a mediator (if implemented as a standalone device), a U2C2 gateway, an endpoint, and/or another server/gateway of FIGS. 1, 10, and 19. Embodiments of the device 2000 include cellular telephones (including smart phones), personal digital assistants (PDAs), netbooks, tablets, laptops, desktops, workstations, servers, telepresence consoles, and any other computing device that can communicate with another computing device using a wireless and/or wireline communication link. Such communications may be direct (e.g., via a peer-to-peer network, an ad hoc network, or using a direct connection), indirect, such as through a server or other proxy (e.g., in a client-server model), or may use a combination of direct and indirect communications. It is understood that the system 2000 may be implemented in many different ways and by many different types of systems, and may be customized as needed to operate within a particular environment.

The system 2000 may include a controller (e.g., a central processing unit (“CPU”)) 2002, a memory unit 2004, an input/output (“I/O”) device 2006, and a network interface 2008. The components 2002, 2004, 2006, and 2008 are interconnected by a transport system (e.g., a bus) 2010. A power supply (PS) 2020 may provide power to components of the computer system 2000, such as the CPU 2002 and memory unit 2004, via a power system 2014 (which is illustrated with the transport system 2010 but may be different).

It is understood that the system 2000 may be differently configured and that each of the listed components may actually represent several different components. For example, the CPU 2002 may actually represent a multi-processor or a distributed processing system; the memory unit 2004 may include different levels of cache memory, main memory, hard disks, and remote storage locations; the I/O device 2006 may include monitors, keyboards, and the like; and the network interface 2008 may include one or more network cards providing one or more wired and/or wireless connections to a network 2016. Therefore, a wide range of flexibility is anticipated in the configuration of the system 2000.

The system 2000 may use any operating system (or multiple operating systems), including various versions of operating systems provided by Microsoft (such as WINDOWS), Apple (such as Mac OS X), UNIX, and LINUX, and may include operating systems specifically developed for handheld devices, personal computers, servers, and embedded devices depending on the use of the system 2000. The operating system, as well as other instructions, may be stored in the memory unit 2004 and executed by the processor 2002. For example, if the system 2000 is an MCU, a mediator, or a U2C2 gateway, the memory unit 2004 may include instructions for performing the applicable methods described herein.

While the preceding description shows and describes one or more embodiments, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present disclosure. For example, various steps illustrated within a particular flow chart or sequence diagram may be combined or further divided. In addition, steps described in one flow chart or diagram may be incorporated into another flow chart or diagram. Furthermore, the described functionality may be provided by hardware and/or software, and may be distributed or combined into a single platform. Additionally, functionality described in a particular example may be achieved in a manner different than that illustrated, but is still encompassed within the present disclosure. Therefore, the claims should be interpreted in a broad manner, consistent with the present disclosure.

For example, in one embodiment, a method for enabling communications between incompatible communication systems includes receiving, by a universal unified communications and collaboration (U2C2) gateway in a first system, a request originating from a first endpoint in the first system, wherein the request invites a second endpoint in a second system that is incompatible with the first system into a unified communications and collaboration (UCC) session with the first endpoint; establishing, by the U2C2 gateway, a connection with a server in the second system in order to communicate with the second endpoint, wherein the U2C2 gateway uses a plurality of protocols and behaviors defined for use by the second system when communicating with the server in order to make the first system appear to be compatible with the second system; notifying, by the U2C2 gateway, a multipoint control unit (MCU) within the first system of the connection, wherein the MCU manages the UCC session and wherein the U2C2 gateway is recognized by the MCU as a source and a destination for communications corresponding to the second endpoint in the UCC session; normalizing, by the U2C2 gateway, media received from the second endpoint via the server for compatibility with the first system before sending the media to the MCU for the UCC session; and normalizing, by the U2C2 gateway, media received from the MCU for compatibility with the second system before sending the media to the second endpoint via the server.

In some embodiments, the U2C2 gateway is configured to communicate with a plurality of systems outside of the first system, the method further comprising determining, by the U2C2 gateway, which of the plurality of systems contains the second endpoint.

In some embodiments, the U2C2 gateway is configured with a plurality of modules that enable the U2C2 gateway to communicate with the plurality of systems, the method further comprising selecting, by the U2C2 gateway, one of the plurality of modules for communication with the second system.

In some embodiments, the request originating from the first endpoint is received by the U2C2 gateway from a mediator.

In some embodiments, the mediator is located on the MCU.

In some embodiments, the request originating from the first endpoint is received by the U2C2 gateway directly from the first endpoint.

In some embodiments, establishing, by the U2C2 gateway, the connection with the server in the second system includes logging into the server as an endpoint of the second system.

In some embodiments, the method further includes receiving, by the U2C2 gateway, a second request originating from the first endpoint, wherein the second request invites a third endpoint in a third system that is incompatible with the first system and the second system into the UCC session; establishing, by the U2C2 gateway, a second connection with a second server in the third system in order to communicate with the third endpoint, wherein the U2C2 gateway uses a plurality of protocols and behaviors defined for use by the third system when communicating with the second server in order to make the first system appear to be compatible with the third system; notifying, by the U2C2 gateway, the MCU of the second connection, wherein the U2C2 gateway is recognized by the MCU as both source and destination for communications corresponding to the third endpoint in the UCC session; normalizing, by the U2C2 gateway, media received from the third endpoint for compatibility with the first system before sending the media to the MCU for the UCC session; and normalizing, by the U2C2 gateway, media received from the MCU for compatibility with the third system before sending the media to the third endpoint.

In another embodiment, a method for enabling communications between incompatible communication systems includes receiving, by a universal unified communications and collaboration (U2C2) gateway in a first system, a request originating from a first endpoint in the first system, wherein the request invites a second endpoint in a second system that is incompatible with the first system into a unified communications and collaboration (UCC) session with the first endpoint; establishing, by the U2C2 gateway, a connection with a server in the second system in order to communicate with the second endpoint, wherein the U2C2 gateway logs into the server as a registered endpoint of the second system in order to be compatible with the second system; notifying, by the U2C2 gateway, a multipoint control unit (MCU) within the first system of the connection, wherein the MCU manages the UCC session and wherein the U2C2 gateway is recognized by the MCU as a source and a destination for communications corresponding to the second endpoint in the UCC session; normalizing, by the U2C2 gateway, media received from the second endpoint via the server for compatibility with the first system before sending the media to the MCU for the UCC session; and normalizing, by the U2C2 gateway, media received from the MCU for compatibility with the second system before sending the media to the second endpoint via the server.

In some embodiments, the method further includes adding a third endpoint in the second system to the UCC session, wherein the U2C2 gateway is recognized by the MCU as the source and destination for communications corresponding to the third endpoint in the UCC session; and upon receiving media from the MCU to send to the second system, dropping any of the media that originated in the second system prior to sending any media originating in the first system to the server.

In some embodiments, the method further includes adding a third endpoint in the second system to the UCC session, wherein the U2C2 gateway is recognized by the MCU as the source and destination for communications corresponding to the third endpoint in the UCC session; and upon receiving media from the MCU to send to the second system, sending the media to the second endpoint only if the media did not originate from the second endpoint, and sending the media to the third endpoint only if the media did not originate from the third endpoint.

In some embodiments, the U2C2 gateway is configured to communicate with a plurality of systems outside of the first system, the method further comprising determining, by the U2C2 gateway, which of the plurality of systems contains the second endpoint.

In some embodiments, the U2C2 gateway is configured with a plurality of modules that enable the U2C2 gateway to communicate with the plurality of systems, the method further comprising selecting, by the U2C2 gateway, one of the plurality of modules for communication with the second system.

In some embodiments, the request originating from the first endpoint is received by the U2C2 gateway from a mediator.

In some embodiments, the request originating from the first endpoint is received by the U2C2 gateway directly from the first endpoint.

In yet another embodiment, a first system includes a universal unified communications and collaboration (U2C2) gateway configured to support a unified communications and collaboration (UCC) session between a first endpoint in the first system and a second endpoint in a second system that is incompatible with the first system, wherein the U2C2 gateway uses a plurality of protocols and behaviors defined for use by the second system when communicating with a server in the second system in order to make the first system appear to be compatible with the second system, and wherein the U2C2 gateway is further configured to communicate with a multipoint control unit (MCU) that is configured to manage the UCC session within the first system, wherein the U2C2 gateway is recognized by the MCU as a source and a destination for communications corresponding to the second endpoint in the UCC session; and a mediator configured to receive requests from endpoints in the first system to add endpoints to the UCC session and to send the requests to the U2C2 gateway.

In some embodiments, the second system is one of a plurality of other systems with which the U2C2 gateway is configured to communicate, and wherein the U2C2 gateway is configured with a plurality of modules that enable the U2C2 gateway to communicate with the plurality of systems.

In some embodiments, the mediator is configured to send the request to the U2C2 gateway only if an endpoint to be added to the UCC session is from a system other than the first system, and is configured to send the request to the MCU if an endpoint to be added to the UCC session is from the first system.

In some embodiments, the U2C2 gateway is configured to log into a server in a third system of the plurality of systems as an endpoint of the third system in order to include a third endpoint in the third system in the UCC session.

In some embodiments, the mediator is located on a separate device from the MCU.

In some embodiments, the mediator is located on the MCU.

In still other embodiments, a system, device, or apparatus includes a network interface, a processor coupled to the network interface, and a memory coupled to the processor and containing a plurality of instructions for execution by the processor, wherein the instructions include instructions for executing any of the methods disclosed herein. 

What is claimed is:
 1. A method for enabling communications between incompatible communication systems, the method comprising: receiving, by a universal unified communications and collaboration (U2C2) gateway in a first system, a request originating from a first endpoint in the first system, wherein the request invites a second endpoint in a second system that is incompatible with the first system into a unified communications and collaboration (UCC) session with the first endpoint; establishing, by the U2C2 gateway, a connection with a server in the second system in order to communicate with the second endpoint, wherein the U2C2 gateway uses a plurality of protocols and behaviors defined for use by the second system when communicating with the server in order to make the first system appear to be compatible with the second system; notifying, by the U2C2 gateway, a multipoint control unit (MCU) within the first system of the connection, wherein the MCU manages the UCC session and wherein the U2C2 gateway is recognized by the MCU as a source and a destination for communications corresponding to the second endpoint in the UCC session; normalizing, by the U2C2 gateway, media received from the second endpoint via the server for compatibility with the first system before sending the media to the MCU for the UCC session; and normalizing, by the U2C2 gateway, media received from the MCU for compatibility with the second system before sending the media to the second endpoint via the server. 